Method and system for telephone message management

ABSTRACT

A system for managing telephone messages played by a telephone includes an integrated telephone answering device configured to playback a plurality of outgoing messages. The system further includes a first memory section to store a default outgoing message and a second memory section to store one or more custom outgoing messages. The system further includes a handset operable to send outgoing messages for storage in the base unit and to send information related to outgoing messages for storage in a database of the base unit, the information including an outgoing message identifier associated with each outgoing message and a list of calling numbers associated with each outgoing message identifier. The system further includes a processor operable to receive an indication of a playback outgoing message request, to determine a calling party number associated with the outgoing message identifier, to retrieve an outgoing message identifier associated with the calling party number, and to send a signal to the integrated telephone answering device to playback an outgoing message associated with the outgoing message identifier.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 12/098,829, filed Apr. 7, 2008, which is herein incorporated byreference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE DISCLOSURE

The present disclosure relates to telephones, and more particularly, forcommunications using a telephone answering device.

BACKGROUND

Many modern telephones are equipped with an integrated telephoneanswering device (ITAD) that is typically integrated within a base unitof a telephone. Known ITADs provide an easy to use interface at the baseunit that allow a user (the ITAD owner and called party) to record amessage to be played to a caller when an incoming call is not picked up.In typical systems, a single short message is played to any caller whenthe phone is not taken off the hook after a predetermined amount ofrings. In known systems, it is possible for the user to initiaterecording and subsequently play recorded messages received from a callerby pressing either a single button, or perhaps two buttons provided onthe base unit. Moreover, the user can typically dial into the telephoneremotely to play messages left in the ITAD, thus providing a convenientmeans for a user to retrieve caller messages. In addition, becauserecording and playback only requires one or two buttons, ITADs can beincorporated into relatively inexpensive base units that have a simpleuser interface. For example, the base unit may simply include buttons tooperate the ITAD and a cradle for a handset.

Typical ITAD systems, however, provide only a limited amount ofinformation to a caller whose call is not answered by a live person.Known ITAD systems typically have a limited amount of storage space fora user to record a message that can give the caller information such asinformation confirming the name or number of the called party anddirections as to how to leave a message. Known ITADs are configured toplay the same general message in response to any incoming call that isnot answered by a live person. Often, however, a user may wish toprovide more timely information to a potential calling party than iscontained in a first, general pre-recorded message, such as informationindicating that the called party is out of town for a period of time, orcurrent contact information that the caller can use to contact thecalled party through other means besides the telephone associated withthe ITAD. However, this requires the user to record a new message forthe ITAD, which replaces the first, general, message and is then playedin response to any incoming unanswered call. When a user returns fromout of town, for example, the user, having replaced the general messagewith a more timely and specific message, then has to reenter a message,such as the first general pre-recorded message, to provide appropriateinformation to calling parties. This process of updating the messageplayed by an ITAD is cumbersome for the called party ITAD user,especially if the update process has to be performed often and is notideally suited to the information needs of a wide variety of potentialcalling parties who may include complete strangers as well as closefamily members.

One attempt to address the above problem, described in U.S. Pat. No.4,985,913 to Shalom et al. (“Shalom”), involved a telephone answeringmachine that included a microcomputer that was connected over a commonbus to a recording device and full alphanumeric keypad with functionkeys. The telephone answering machine facilitated recording severaldifferent messages and facilitated assigning of a user telephone numberto one of the several messages so that a message could be played basedon the identified phone number.

Another example of an answering machine where more than one message canbe played back is described in a series of patents to Gerszberg et al.(“Gerszberg”), namely, U.S. Pat. Nos. 6,226,362; 6,377,664; and6,385,305. The latter machine included a video display and capabilityfor playback of video announcement messages.

However, both Gerszberg and Shalom disclose relatively complexprocedures and hardware systems that cannot readily be incorporated intotypical home phones having a simple base unit where the user interfacemay be of minimal complexity.

SUMMARY

In accordance with an aspect, a system for managing telephone messagesplayed by a telephone includes an integrated telephone answering deviceconfigured to simultaneously store a plurality of outgoing messages(OGMs). In one aspect, the integrated telephone answering device isincluded in a base unit of a telephone. The system further includes amemory located in the base unit for receiving from a handset and storingin a data structure information related to outgoing messages, such as anoutgoing message identifier associated with at least one of the outgoingmessages, and a list of calling numbers associated with each outgoingmessage identifier. Preferably, the system further includes a userinterface located in a handset of the telephone and designed to allow auser to view information, such as calling party and OGM identifiers, andto select and enter calling party phone numbers for storage in a datastructure that associates the calling party phone number with an OGMidentifier. The system further includes a processor operable to receivean indication of a request to playback an OGM to determine a callingparty number associated with the playback OGM message, to retrieve anOGM identifier associated with the calling party number, and to send asignal to the integrated telephone answering device to playback an OGMassociated with the OGM identifier.

Accordingly, the system can retrieve and playback an OGM tailored to acaller associated with the calling party number.

In accordance with another embodiment, a method for managing outgoingtelephone messages in a telephone comprises a step of storing aplurality of outgoing messages in an integrated telephone answeringdevice that is located, for example, in a base unit of the telephone. Inone aspect, all outgoing messages save a default message are entered forstorage in the integrated telephone answering device using a handset ofthe telephone. The method further involves storing a plurality ofoutgoing message indicators in a memory wherein each outgoing messageindicator is associated with a respective outgoing message. In a furtherstep, a calling party number is stored in a memory such that the callingparty number is associated with a selected outgoing message indicator.In one aspect, all outgoing message indicators and associated callingparty numbers are stored into a data structure of a base unit by using ahandset of the telephone to transmit the outgoing messages indicatorsand associated calling party numbers to the base unit. In a furtherstep, a signal to play an outgoing message in response to an incomingtelephone call is received. A calling party number associated with theincoming telephone call is determined. An outgoing message indicatorassociated with the calling party number is retrieved and a signal issent to play the respective outgoing message corresponding to theretrieved outgoing message indicator.

In a further embodiment, a method for managing an integrated telephoneanswering device comprises storing a plurality of outgoing messages inthe integrated telephone answering device. A selected outgoing messageis stored as a default outgoing message. A signal to playback anoutgoing message in response to an incoming call is received. A memorystructure comprising one or more calling party numbers and a pluralityof outgoing message indicators associated with respective outgoingmessages is queried. If a calling party number associated of theincoming call is found in the memory structure, the outgoing messageindicator associated with the calling party number is retrieved and asignal to play the corresponding outgoing message is sent to theintegrated telephone answering device. If the calling party number isnot found in the memory structure, a signal to play the default outgoingmessage is sent to the integrated telephone answering device.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned and other features and advantages of this disclosureand the manner of attaining them will become more apparent, and thedisclosure itself will be better understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings.

FIG. 1 depicts in schematic form a system for managing outgoingtelephone messages, in accordance with an embodiment.

FIG. 2 illustrates an example of a phone book data structure containedin a handset and a related OGM data structure contained in a base unit,in accordance with an embodiment.

FIG. 3 illustrates exemplary steps involved in a method for managing

DETAILED DESCRIPTION

The present disclosure will be described with reference to theaccompanying drawings. Corresponding reference characters indicatecorresponding parts throughout the several views. The description as setout herein illustrates an arrangement of an embodiment of the presentdisclosure and is not to be construed as limiting the scope of thedisclosure in any manner.

Embodiments of the present disclosure provide a system and method formanaging outgoing messages (OGMs) that are provided to a calling partywho dials a telephone number associated with a called party. Asdescribed in detail with respect to the figures, the system and methodof the present disclosure allow a user to conveniently store and selectfor playback an OGM from a plurality of OGMs, such that the selected OGMis tailored according to the potential calling party, that is, theselected OGM is specific to the calling-party (also termed “caller”).The system also provides a means for automatic playback of acaller-specific OGM selected from a plurality of OGMs where thecaller-specific OGM is played in response to an unanswered incomingphone call received at a called party telephone.

The system is capable of being incorporated with little hardwaremodification of known configurations of telephones, such as telephoneshaving a simple base unit and handset. For example, by distributinghardware and programming functions related to management of OGMs,between a handset and a base unit, a base unit equipped with an ITAD canbe configured to provide a variety of calling party-specific OGMswithout the need to incorporate complicated user interface hardware inthe base station.

FIG. 1 depicts a system 100 for managing outgoing telephone messages, inaccordance with an embodiment. System 100 includes a base unit 110 and ahandset unit 120 that is configured to communicate with base unit 110over a wireless link. In one embodiment, system 100 is a cordlesstelephone system in which base unit 110 is a cordless base unit that isconfigured to communicate with handset 110 using a DECT, WDCT, or otherwireless communications protocol that is designed for localcommunication (communication range generally less than about 1000meters).

In the embodiment depicted in FIG. 1, base unit 110 includes anintegrated telephone answering device (ITAD) 112 that is configured toplay an outgoing message in response to an incoming call received attelephone 100 (the terms “system 100” and “telephone 100” are usedinterchangeably hereinafter). For example, ITAD 112 can be set to playan outgoing message if telephone 100 is not taken off-hook after apredetermined interval, which denotes for example, a predeterminednumber of rings received from an incoming call, or a predeterminedamount of time from when the incoming call is detected at phone 100.ITAD 112 is preferably further configured to receive and store incomingmessages from calling parties who may leave a message in response to theplayed outgoing message.

In accordance with an embodiment, ITAD 112 is configured to play acaller-specific OGM that is chosen from one of a plurality of storedOGMs. The term “caller-specific OGM” refers to the fact that the systemis configured to determine which of a plurality of OGMs to play basedupon at least one specific feature associated with an incoming callingparty (caller), as described further below.

For example, a user may wish to record for playback two or moredifferent type of OGMs: a first OGM (default OGM) to be used for “thegeneral public” may include a standard message asking the calling partyto leave a message, while a second OGM designed for close friends andfamily may provide additional information, such as a cell phone numberor likely whereabouts. Another type of OGM a user may wish to record forplayback is a short-term or one-off message designed only for aparticular caller. By storing a plurality of OGMs and providing a meansto select which OGM to play in response to an incoming call, thedisclosed system thus facilitates the ability to provide more usefulinformation to selected calling parties than may typically be containedin a generic OGM, while at the same time restricting information givento other callers, such as unknown callers or known callers for whom onlylimited information is to be given.

In one embodiment, system 100 is configured to select for playback acaller-specific OGM based upon the phone number of the incoming call.Thus, system 100 is operable to determine the phone number of anincoming calling party and to thereby determine an appropriate OGM to beplayed back to the calling party based upon the incoming phone number.

In accordance with embodiments, base unit 110 provides a means forstoring a default OGM in a separate region or section of memory asopposed to custom OGMs, such as those designed for friends, family, orone-of-a-kind OGMs. The storage of custom OGMs separate from a defaultOGM affords benefits in management of OGMs, as described further below.

FIG. 1 illustrates that base unit 110 further includes a memory 114,which includes information related to potential calling parties andinformation related to the plurality of OGMs stored by ITAD 112. Memory114 could be more than one memory device and could be disposed withinITAD 112 or in a separate part of base unit 110. Preferably, the callingparty information stored in memory 114 includes a list of caller phonenumbers, and one or more OGM identifiers, as described further below.The list of caller phone numbers can include a plurality of caller phonenumbers, wherein one or more of the plurality of phone numbers can beassociated with an OGM identifier. The OGM identifier stored in memory114 can be, for example, a descriptive word that is linked to a specificOGM stored in ITAD 112. For example, a first identifier could be “familymessage” and second identifier could be “general message.”Alternatively, the identifiers could simply be “OGM1,” “OGM2,” and thelike.

In one embodiment, memory 114 is part of the ITAD and is configured tostore OGMs therein, in addition to calling party information.

Base unit 110 further includes a processor 116 (which can be more thanone processor) that is operable to identify an incoming phone number,for example, using known caller ID functionality. Processor 116 isfurther operable to query memory 114 and to assign an OGM to theincoming phone number based on the memory query. Accordingly, after aphone number of an incoming call is identified, memory 114 can besearched to see if the incoming phone number is contained therein. Basedon the results of the search, as described in detail below, processor116 then assigns for playback a specific OGM tailored for the callingparty corresponding to the incoming phone call. For example, processor116 could ascertain that a first incoming phone number is contained inmemory 114 and corresponds to an “OGM3” that is a message to be playedfor family members of the called party. Accordingly, processor 116 cansend a signal to ITAD 112 to play “OGM3” if the first incoming call doesnot go off-hook after five rings, for example. Processor 116 could befurther configured such that if a second incoming call is determined tocorrespond to a phone number that is not contained in memory 114, thecall is assigned to an “OGM1” corresponding to a generic outgoingmessage. Accordingly, processor 116 can send a signal to ITAD 112 toplay “OGM 1” if the second incoming call does not go off-hook after fiverings, for example.

Although the above-mentioned functionality could be programmed within aprocessor 116, in other embodiments, processor 116 could be configuredto invoke and perform the steps of a separate software program thatembodies the functions described above in response to an incoming phonecall.

Base unit 110 also includes a microphone 118 that allows a user torecord an OGM to be stored in ITAD 112. This could be accomplished byproviding a record button 119 or other simple means that activatesrecording of a message using microphone 118.

In one embodiment, the OGM recorded by the base unit is stored as the“default” OGM in ITAD 112. The default OGM represents an OGM that isplayed back by ITAD 112 in response to any unanswered incoming call,unless system 100 determines that the phone number of the incoming callis associated with an OGM different from the default OGM. Thus, forexample, for incoming calls associated with phone numbers that are notcontained in memory 114, ITAD 112 can be configured to playback thedefault OGM.

In one embodiment, base unit 110 is configured so that only a singlemessage recorded by base unit 110 is stored at any one time. Inaccordance with this embodiment, the telephone system 100 could beconfigured such that other OGMs, that is, “special” OGMs that are linkedto specific phone numbers only, could be recorded only through use ofhandset 120 whose operations are described in detail below. In thismanner, a user operating base unit 110 could be restricted to onlyrecording and modifying a default OGM, In other words, base unit 110 canbe configured such that only a single message received throughmicrophone 118 can be stored for playback in ITAD 112 at any one time.For example, as described further below, base 110 can be configured suchthat it recognizes a select portion of storage space in ITAD 112 to beoccupied by a default OGM. Any message recorded through microphone 118would accordingly be stored in the select portion of storage space andreplace the previous default OGM previously recorded there. Thus,besides button 119, a user interface of base unit 112 need not include akeypad, display, or additional soft keys that would facilitate, forexample, designation, recording, and simultaneous storage of multipleoutgoing messages.

In accordance with an embodiment in which memory 114 is designed forstoring OGMs, memory 114 is provided with a first section 114 a forstoring a default OGM and a second section 114 b that is separate fromsection 114 a for storing custom OGMs. For example, a default OGM couldbe recorded through microphone 118. In this embodiment, when a userpresses button 119 to record a new default OGM, base unit 110 recognizesthat button 119 has been depressed and thereby knows that the OGM beingrecorded is to be stored in section 114 a. Section 114 a of memory 114preferably is configured with sufficient memory for the user to record adefault message of a reasonable length, for example, sufficient memoryto store a 90 second message. Because the default OGM is to be storedseparately from custom OGMs, which are stored in section 114 b, the useris assured that there will always be space available to record thedefault OGM, and need not have any knowledge of whether any custom OGMsare stored in memory 114 or what the length of such messages might be.Accordingly, recording and re-recording of default OGMs can proceedthrough simply touching a record button 119.

In accordance with an embodiment, a user can also record the default OGMfor storage in memory section 114 a using handset 120, as described inmore detail below.

In accordance with one embodiment, any OGMs to be stored in memorysection 114 b must be recorded through handset 120. For example, in oneembodiment in base unit 110, button 119 comprises the only userinterface available for recording and storing OGMs using base unit 110.In accordance with the embodiment described above, in which OGMsrecorded through button 119 are directed to memory section 114 a, a useris therefore precluded from recording OGMs for storage in memory section114 b using base unit 110.

Memory section 114 b can be apportioned with sufficient memory to recorda plurality of OGMs. Accordingly, as described below, a user can recordone or more custom OGMs for storage in memory section 114 b through ahandset 120. In accordance with an embodiment, if memory section 114 bbecomes full while a user is recording a custom OGM, the user can beprompted to free up memory space in memory section 114 b if the userwishes to extend the OGM being recorded.

Referring now to handset 120, in accordance with embodiments, handset120 is operable to receive, store, manipulate and transmit to base unit110 OGMs and information related to OGMs to be stored in base unit 110.In accordance with embodiments, handset 120 can represent one of aplurality of similar cordless handsets in a cordless telephone system.

In accordance with one embodiment, handset 120 is configured such thatOGMs and OGM-related information entered and manipulated by handset 120are not permanently stored in the handset. However, in otherembodiments, handset 120 can be configured to store OGMs, OGM-relatedinformation, or both.

In particular, in accordance with embodiments, handset 120 is configuredto allow a user to establish a data communication session with base unit110 to perform one or more or the functions numbered immediately below.The data communications session can be established over a radiofrequency link between handset 120 and base unit 110. According to anembodiment, in a system 100 having a plurality of handsets 120, only onedata communications session can be established at a time to avoidconflicting communications with a base unit.

Handset 120 can be configured for:

1) Recording and transmitting one or more custom OGMs for storage inbase unit 110. In accordance with embodiments, a user can record an OGMusing handset 120 and transmit the recorded OGM to base unit 110 whilethe communication session is active. In accordance with embodiments, thelocation for storage of an OGM recorded in handset 120 can be determinedeither automatically or with the aid of input received from the user.For example, system 100 could be configured so that any recorded OGMtransmitted from handset 120 to base unit 110 is allocated by default tosection 114 b, the portion of memory for “custom” OGMs. Accordingly, inthe absence of any user input, during recording of a streamed OGM orafter an OGM is recorded by the user in handset 120, the recorded OGM issent to base unit 110 for storage in memory section 114 b. A userwishing to record an OGM for storage and use as the default OGM inmemory section 114 a, would thereby have to enter an affirmativeindication that the current OGM to be transmitted from handset 120 tobase unit 110 is to be stored as the default OGM. Alternatively, thehandset 110 could be configured to require a user to select adestination for any recorded OGM, such that an OGM recorded at handset120 would not be transmitted and stored at base unit 120 until adesignation for storage as a custom OGM or a default OGM was entered,which would trigger the base unit to 110 to direct the received OGM to arespective memory sector 114 b or 314 a.

2) Retrieving OGM-related information from base unit 110. As describedin detail below, OGM-related information that is stored in memory 114 ofbase unit 110 can be retrieved by handset 120 during a datacommunications session.

3) Viewing the OGM-related information. Handset 120 is configured with adisplay 128 for viewing OGM-related information retrieved from base unit110.

4) Manipulating the OGM-related information. As described in detailbelow, handset 120 is provided with means to manipulate the OGM-relatedinformation retrieved from base unit 110. The manipulation could involveupdating a caller list with corresponding OGM identifiers andsubsequently displaying the updated list to the user on display 128.

5) Sending any updated OGM-related information to base unit 110 forstorage. During a data communications session, updated or newOGM-related information can be sent to base unit 110 for storage.

In addition, in embodiments in which handset 120 is configured to storeOGMs or OGM-related information, handset 120 could be configured toperform such storage operations either during a data communicationssession with base unit 110 or at a time in which no data communicationssession is active.

Referring again to FIG. 1, handset 120 includes a microphone 124 thatallows a user to locally record one or more OGMs, and a radiotransceiver 126 that is configured to transmit recorded OGMs and otherOGM-related information to base unit 110 via transceiver 121. Inaccordance with one embodiment, once a data communications session (alsotermed “data session” herein) is established between handset 120 andbase unit 110, handset 120 is configured to stream an OGM from handset120 to base unit 110 during recording of the OGM through microphone 124,such that the OGM is not stored permanently in handset 120. Accordingly,handset 120 need not include memory space necessary to store one or moreOGMs. However, as mentioned above, in other embodiments, handset 120could be configured with memory to store OGMs locally in the handset.

In accordance with one embodiment, by providing a separate memorysection 114 b in base unit 110 for storage of custom messages, byrequiring that messages to be stored in memory section 114 b be enteredthrough handset 120, and by requiring an affirmative indication from auser of handset 120 that a recorded OGM is to be used as a default OGM,system 100 provides several advantages. As noted above, the user of baseunit 110 is provided with a simple interface (button 119) for recordingand re-recording a default OGM. The user is additionally provided withthe flexibility of recording custom OGMs without the need of having acomplex user interface on base unit 110. Moreover, the user is assuredthat the default OGM will not inadvertently be erased during operationsto record custom OGMs, since the only way to erase the OGM stored inmemory 114 a is through use of the base unit 110, or through anaffirmative selection at handset 120, both of which operations would putthe user on notice that the default OGM is being erased.

In accordance with another embodiment, while an OGM message is beingrecorded and streamed to base unit 110, display 128 can be configured toalert a handset user if the memory space in memory 114 b is full, sothat the user can direct base unit 110 to free up space in memory 114 b,if desired, to accommodate a new custom OGM. For example, base unit 110could be configured to detect when the used space in memory 114 bexceeded a threshold and to dynamically send an alert to handset 120during a data communications session. Alternatively, a user can beprovided with a menu means on handset 120 to query from base unit 110the amount of memory (expressed for example in terms of recording time)available in memory 114 b, the result of which query could be sent todisplay 128.

Thus, in accordance with an embodiment, by partitioning the recording ofdefault OGMs and custom OGMs between respective base unit 110 andhandset 120, system 100 facilitates a convenient and safe process forstoring the default OGM, while at the same time facilitating aconvenient process for recording and storing custom OGMs, without thenecessity of having a complex user interface in base unit 110.

In accordance with an embodiment, during a data communications session,based on user input, handset 120 is configured to retrieve OGM-relatedinformation contained in memory 114 of base unit 110, to manipulate theretrieved information, and to resend the manipulated retrievedOGM-related information to the base unit 110 over the radio frequencylink for storage. Such information can be stored in a data structurethat includes OGM-related information, such as a list of OGM identifiers(e.g., OGM1, OGM2, and the like, or family, general, work, and thelike). The term “data structure,” as used herein, refers to any table,database, or electronic phone book, among other things, that storesinformation in an organized manner, wherein one type of information iscorrelated to another type of information. For example, the terms“outgoing message data structure,” “OGM data structure,” “outgoingmessage database,” or “OGM database” each denote a table that isconfigured to include at least one OGM identifier and at least one pieceof calling party information associated with that OGM identifier. Atleast one program or similar process that can access such a datastructure is operable to correlate the OGM identifier to one or morepieces of calling party information.

As described in more detail below, in accordance with some embodiments,an OGM data structure includes a list of phone numbers that are eachlinked in the data structure to a specific OGM. In one embodiment, thedata structure can be organized as a phone book-type structure thatincludes a plurality of calling party entries that each can includecaller information such as caller phone number, caller name, otherpersonal caller information, OGM identifier and ring tone to be played.If base unit 110 is not provided with a user interface to access ormanipulate the OGM data structure, viewing and manipulation of such adata structure is performed solely through a handset 120.

In addition, in an embodiment, system 100 is configured such that allcalling party information and OGM identifier information stored inmemory 114 of base unit 110 is entered through handset 120. Thus,management of an OGM data structure located in base unit 110, as well asmanagement of custom OGMs stored in base unit 110, is performed entirelyby handset 120, even when handset 120 contains no provision forpermanent storage of OGMs or OGM-related information. This averts thenecessity of providing a complex user interface in base unit 110 thatwould be necessary to record and allocate a plurality of different OGMsfor ITAD 112 and to program OGM data structures in memory 114.

As mentioned above, handset 120 further includes a display 128, whichcan be used for visually displaying information, such as calling partyphone numbers, OGM identifiers, programming prompts, and the like. Inaccordance with embodiments, handset 120 includes user interface 130,which can include an alphanumeric key pad, scroll or other selectiondevices, and hot keys.

Handset 120 additionally contains a processor 132 that is configured toprogram information for storage in an OGM data structure contained inmemory 114. In alternative embodiments, an OGM data structure can alsobe contained in memory 122. In accordance with an embodiment, handset120 is configured to allow a user to designate OGM-related informationto be sent to base unit 110. For example, in one aspect, a programstored in handset 120 is operable to allow a user to manipulateinformation retrieved from an OGM data structure of base unit 110 duringa communications system. Thus, in accordance with the presentdisclosure, programming and updating an OGM identifier list, callingparty numbers, and the like that are located in base unit 110, can beaccomplished by using user interface 130 of handset 120. User interface130 allows the handset user to initiate a data communications session,retrieve desired OGM-related information from base unit 110 during thedata session, modify the OGM-related information retrieved from baseunit 110, and enter and send new OGM-related information or modifiedOGM-related information for storage in base unit 110.

In one embodiment, handset 120 includes a program or routine that allowsa user to record a new OGM. The program or routine can be launched, forexample using a combination of interface 130 and display 128. Forexample, display 128 can contain a main menu that allows the user toaccess, including an OGM menu, by use of interface 130. When the userselects an option in the OGM menu to record a new OGM recording isactivated, and a message can be recorded through microphone 124. In oneaspect, the program automatically prompts the user to name the newlyrecorded OGM, that is, to enter an OGM identifier. This OGM identifiercan then be stored in a data structure, such as an OGM table or aphone-book that can include fields related to calling parties, asdiscussed further below. In another aspect, the program couldautomatically assign an OGM identifier to a newly-recorded OGM, such as“OGM4,” which could be displayed to the user as a reminder at the timethe new OGM is recorded.

FIG. 2 illustrates the relation between a data structure 200 in handset120 and a corresponding data structure 220 stored in base unit 110, inaccordance with an embodiment. Data structure 200 (also termed “phonebook”) can be part of a phone book-type data structure that containscaller information, such as caller phone number and personalinformation. As such, data structure 200 as depicted in FIG. 2 cancomprise a plurality of calling party entries, such as entry 210, whereeach entry (or “record”) corresponds to a row in the data structure, andeach row contains information from one or more of a plurality of fieldsthat each contain a specific type of information related to callingparties. Field (column) 202 contains a plurality of caller phone numbersthat can each be stored by known methods, or alternatively, inaccordance with methods described below.

Field 204 can contain conventional caller personal information, such asname and address. For clarity, in the example illustrated in FIG. 2,only name information is shown in field 204. In accordance with anembodiment, each calling number entry in field 202 can have acorresponding entry in field 204.

A user can use phone book 200 to access a contact's phone number. Forexample, a user may be presented with a “phone book” menu that allowsthe user to scroll through a list of names, in order to find a desiredcontact's phone number, by selecting the contact name from the list.Although only a few entries are depicted in field 202, it will bereadily appreciated that a phone book 100 could contain many hundreds orthousands of entries in both fields 202 and 204.

In accordance with an embodiment, the data stored in data structure 220in memory 114 of base unit 110 can only be entered and/or modified usinghandset 120. For example, base unit 110 may not have an appropriate userinterface, such as a keypad and display that would facilitate entry ofsuch information. Accordingly, the information to be stored in datastructure 220 is initially entered through handset 120 and thenforwarded to base unit 110 during a data communications session. Inaccordance with embodiments, a user of handset 120 could select fromentries in phone book 200 to update data structure 220 of base unit 110.

As depicted, data structure 220 in memory 114 of base unit 110 containsthe same field 202 as in data structure 200. However, field 202 of datastructure 220 need not contain the same amount of telephone numberentries as stored in data structure 200. In accordance with anembodiment, data structure 220 only contains phone numbers that areassociated with an OGM identifier, as depicted in field 206 of datastructure 220. In accordance with the embodiment depicted in FIG. 2,personal information field 204 is absent from data structure 220. Thisallows memory 114 to be smaller than would be required if all personalinformation of phone book 200 were stored locally in memory 114.

In accordance with an embodiment, when a user of handset 120 wishes toupdate data structure 220 in base unit 110, the user can sendinformation contained in phone book 200 to base unit 110. For example, auser may wish to assign a pre-existing OGM to a contact contained in theuser's phone book 200 of handset 120. In the example illustrated in FIG.2, the user may wish to assign an outgoing message (OGM3) to contactMaggie Jones so that when Maggie Jones subsequently places an unansweredtelephone call to system 100, OGM3 will be played by ITAD 112. Inaccordance with alternative embodiments, the user could accomplish thiswith the aid of a phone book routine or a stand-alone “OGM” routineoperable in handset 120.

In one embodiment, the user could launch a phone book 200 routineprovided on handset 120, which could provide a series of contactentries, such as entry 210, that each include phone numbers of contactsand names of contacts. Although a handset display could be configured todisplay the entire entry 210, in one implementation, handset 120 onlydisplays the user list 204 that contains user names alone. When the userreaches the desired name, the user could select the name, whereby aprogram operable in handset 120 could provide a series of menu options,among them a prompt to the user to see if the user desired to associatethe name with an OGM identifier. If so, the user could be provided witha list of OGM identifiers, such as the OGM identifiers in list 206. Theuser would then select ‘OGM3,’ after which handset 120 knows to forwardinformation related to Maggie Jones and OGM3 to base unit 110, which isrecorded as entry 210 a. The user need not know nor view the phonenumber of Maggie Jones in order for handset 120 to forward the phonenumber to base unit 110, since the phone number is already associatedwith Maggie Jones in record 210 of phone book 200, as depicted in FIG.2. When the user enters a command or the handset 120 otherwise triggersa synchronization operation, handset 120 forwards information fromrecord 210 for storage in data structure 220 of base unit 110. Inaccordance with alternative embodiments, system 100 can be configured toprompt the user to send the newly-updated information to base unit 110,or, alternatively, can be configured to automatically send theinformation to base unit 110. Because exemplary data structure 220, asshown in FIG. 2, is only configured to store calling party number andOGM identifier information, not all the information in Maggie Jonesrecord 210 is copied into a corresponding data record 210 a of datastructure 220. Accordingly, the contact name does not appear in datarecord 210 a.

In another embodiment, an OGM program separate from a phone book programprovided on handset 120 could be configured to allow a user to enter acaller phone number either manually through a keypad or from a phonebook that can be launched from within the OGM program.

In accordance with further embodiments, such operations to add or modifya record containing OGM-related information, such as record 210, can beperformed by a user selecting a menu option through a combination of hotkeys in user interface 130 or selecting menu items provided on display128 that, once selected, allow the user to type information for storagein data structure 200. In other embodiments, entry of information intoan OGM data structure can be assisted by prompts from the phone system,as described further below.

In accordance with embodiments in which data structure 220 only containsfields 202 and 206, data structure 220 can contain a large number ofrecords, such as 210 a, without requiring a large amount of memory,since each record only contains a phone number and an OGM identifierwhich can be limited to a brief set of alphanumeric symbols inaccordance with the present disclosure. Accordingly, a base unit canstore only the necessary information for providing a caller-specific OGMto a large number of calling parties without requiring a large memory.

In other embodiments, a data structure similar to data structure 220could be stored in handset 120.

FIG. 3 illustrates exemplary steps involved in a method 300 for managingoutgoing messages of a telephone, according to an embodiment. In step301, a base unit stores information received from a handset including atleast one OGM identifier and calling party numbers associated with theat least one OGM identifier.

In step 302, a signal is received to play an OGM. This would occur, forexample, when the call is not picked up after a predetermined interval,such that the system generates a signal that an outgoing message shouldbe played.

In step 304, if the calling number of an incoming call is notdetermined, for example, if it is blocked, the process moves to step308. If the calling number is determined, for example, using caller IDtechnology, the process moves to step 306.

In step 306, the signal that an outgoing message should be playedtriggers the system to determine if the calling party number iscontained in the data structure containing the at least one OGMidentifier, such as a phone book-type structure. For example, base unit110 could query data structure 220 to determine if an identified callingparty number is contained therein.

If the calling party number is not found in the data structure, theprocess moves to step 308 where a signal is sent to play a default OGM.If the calling party number is found, the process moves to step 310.

In step 310, the system checks to see if the data structure contains anOGM identifier corresponding to the calling party number. If no OGMidentifier corresponding to the calling party is found in the datastructure, the process moves to step 308 where a signal is sent to playa default OGM. If an OGM identifier corresponding to the calling partynumber is found, the process moves to step 312.

In step 312, a signal is sent to an ITAD in the phone system to play anOGM corresponding to the OGM identifier found in step 310.

It will be apparent to one of ordinary skill in the art that steps inthe method described in FIG. 3 can be embodied in software, such as aprogram or routine, stored on a computer readable medium. For example, aroutine that embodies steps 302-312 could be invoked every time anunanswered call triggers a signal that an OGM should be displayed.

In accordance with further embodiments, a handset, such as handset 120is provided with a user interface, such as user interface 130 that canbe used in conjunction with display 128 to facilitate programming ofOGM-related information to be stored in handset 120 and/or base unit110. For example, a program that allows a user to enter, delete ormodify OGM related information can be launched by selecting a key inuser interface 130 or a field displayed in display 128. For example,after selecting “OGM program,” a main menu displayed on display 128could offer options to record a new OGM, or to view a list of OGMidentifiers corresponding to OGMs already stored in system 100. In oneembodiment, in addition to the list of OGM identifiers, such as OGM1,OGM2, and OGM3, information associated with each OGM could be displayednext to the OGM identifier, such as the date and time recorded andmessage length. In addition, the total amount of available record timein the ITAD could be displayed on display 128.

A menu displayed on display 128 could further offer the user the choiceof switching the default OGM from one OGM to a different OGM. Forexample, the default OGM could be indicated by a bullet, radio button,or other indicator in a view that displays the full list of OGMidentifiers. The user could then scroll to a particular OGM entry toselect or deselect the default OGM.

A main menu or sub-menu could further provide an option to delete anentire data structure, such as a table having a list of “special” OGMs,such that all incoming numbers would automatically trigger playing ofthe default OGM only. In such a case, a program could be configured toconfirm this selection so that the entire table of special OGMs andrelated calling numbers is not inadvertently deleted.

In accordance with embodiments, a user can enter and modify OGM-relatedinformation into a phone system, such as system 100, in a variety ofways. In one method, a user can simply access a menu in a handset, suchas handset 120 that allows the user to enter calling party and OGMinformation through a combination of key entry and/or selection frommenu choices. A user could access, for example, a menu that allowsmanual entry of a calling party phone number to be stored in an OGMdatabase. For example, the user may enter the phone number of a newacquaintance of the user and an indicator of the OGM to be played. Thenew acquaintance may be a new work colleague who is to receive an OGMdesigned for colleagues of the user, such as OGM2, which is then enteredtogether with the other information related to the acquaintance.Alternatively, as described above, the user could designate a callingparty phone number for storage with an appropriate OGM identifier byselection of a caller name from a pre-existing phone book entry selectedby scrolling through a phone book.

In accordance with another embodiment, a user could be presented with anoption to dynamically add or subtract an entry related to a callingparty to an OGM data structure.

For example, a caller ID program operable to detect and display on ahandset or base unit screen an incoming calling number could alert auser to an incoming call, either in real-time or in a call log. Once theuser selects the calling party name corresponding to the incoming call,for example, at a handset display, the user could be prompted, amongother things, to add the incoming calling party to a table or phone bookcontaining a list of OGM identifiers. If the user selects an option toadd the calling party to an OGM data structure and the OGM datastructure is only located in the base unit, the handset could thenestablish a data communications session with the base unit to update theOGM data structure. For example, during the data communications session,the system could then check to determine that the incoming calling partynumber corresponding to the calling party name sent from the handset isnot contained in the OGM data structure, and thereby trigger a prompt toquery the user as to whether the user wishes to associate the incomingcaller with an OGM identifier. Thus, if desired, the user could add theincoming number associated with the calling party in the call log to atable to associate the incoming number with a desired OGM identifier.For example, the user might recognize the incoming number as onebelonging to a work colleague and might wish to add it to the list ofcalling numbers associated with the “OGM2” that is intended for workcolleagues. Accordingly, by highlighting the incoming number, the usercould be prompted to add the calling number to one of a plurality ofOGMs that are displayed to the user.

In the above-described manner, the user can update and build an OGMtable or database by a combination of actions such as highlightingalready displayed telephone numbers on a call log display, scrollingthrough a list of calling numbers, and pressing “enter” or similarprocedures to store a calling number in an OGM table without having totype alphanumeric keys to build an extensive amount of alphanumericentries, such as an entire phone number. Moreover, the phone numbercorresponding to a new OGM entry can correspond to a calling partynumber already stored in the user's phone, such as in a phone book-typedatabase. For example, a user may recognize a calling party numberdisplayed on the handset as coming from a relative and may wish to storethis in the user phone book. By selecting to store the calling partynumber of the user's relative under a section of an OGM tablecorresponding to “OGM3,” the relative's phone number is linked to amessage OGM3 wherein future unanswered calls received from that relativetrigger playback of OGM3.

In addition, in accordance with an embodiment, the selection of OGM3 forlinking to the relative's phone number could automatically place an OGMidentifier corresponding to OGM3 in another type of database, such as acomprehensive phone book data structure that already contains therelative's calling party number. For example, referring again to datastructure 200 of FIG. 2, the selection of OGM3 could result in theaddition of an identifier, such as “OGM3” being added to field 206 in arow corresponding to that already containing the relative's phone numberand personal information.

Accordingly, a phone book-type data structure containing OGM identifiersand/or a simple OGM table could be supplemented or constructed graduallywith the aid of a call log in a telephone so that the user need notenter phone numbers completely manually.

Similarly, a phone system, such as handset 120, could be configured toprovide a prompt to a user to delete an incoming calling party phonenumber from a pre-existing entry in an OGM table, For example, inaccordance with an embodiment, the phone system could be programmed todetermine whether the incoming number is contained in an OGM table, andif so, to automatically prompt the user as to whether the user wishes todelete the incoming number from that table. However, in otherembodiments, the telephone system is configured such that the user mustactively select a calling party number for deletion from an OGM table,wherein no prompt is automatically given to the user to delete anincoming calling party number that is already contained in an OGM table.For example, an incoming calling party number could be displayed in acall log. By selection of a calling party number, the user could beprovided with a menu that allows the user to select from options such as“listen to message,” “store #,” and “delete # from OGM table.”

In accordance with the above-described procedures, programming of phonenumbers and associated OGM identifiers to be stored, modified or deletedfrom a data structure of a base unit can be accomplished using a handsetlinked to the base unit without extensive use of alphanumeric keys. Forexample, the user need only update an OGM data structure of the handsetwhen incoming phone numbers are displayed in a call log or during anactive call, followed by performing a synchronization of the handset OGMdata structure with that of the base unit, as described above.

In accordance with an embodiment, instructions adapted to be executed bya processor to perform a method are stored on a computer-readablemedium. The computer-readable medium can be a device that stores digitalinformation. For example, a computer-readable medium includes a magneticmemory, a semiconductor memory, such as flash memory or DRAM, read-onlymemory (e.g., a Compact Disc-ROM, and the like), as is known in the artfor storing software. The computer-readable medium can be accessed by aprocessor suitable for executing instructions adapted to be executed.The terms “instructions configured to be executed” and “instructions tobe executed” are meant to encompass any instructions that are ready tobe executed in their present form (e.g., machine code) by a processor,or require further manipulation (e.g., compilation, decryption, orprovided with an access code, and the like) to be ready to be executedby a processor.

The foregoing disclosure of the embodiments of the present disclosurehas been presented for purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseforms disclosed. Many variations and modifications of the embodimentsdescribed herein will be apparent to one of ordinary skill in the art inlight of the above disclosure.

Further, in describing representative embodiments of the presentdisclosure, the specification may have presented the method and/orprocess of the present disclosure as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible.

What is claimed is:
 1. A cordless telephone system, comprising: a baseunit; and a handset configured to wirelessly place and receive calls viathe base unit; wherein the base unit is configured to store a defaultoutgoing message in a first memory section and to store a customoutgoing message in a second memory section; wherein the cordlesstelephone system determines that a calling party number of a call is notcontained in an outgoing message identifier database of the base unitand provides a prompt during the call to associate the calling partynumber with an outgoing message identifier of a database.
 2. The systemof claim 1, wherein the base unit further comprises an outgoing messageidentifier database comprising outgoing message identifiers receivedfrom the handset, wherein each outgoing message identifier correspondsto a respective custom outgoing message and at least one calling partynumber; and wherein the base unit is further configured to receive anotification of a calling party number associated with an incomingtelephone call, to retrieve from the database an outgoing messageidentifier associated with the calling party number, and to play anoutgoing message associated with the retrieved outgoing messageidentifier if the incoming call is not answered after a predeterminedinterval.
 3. The system of claim 2, wherein the database comprises aplurality of calling party entries that each includes a caller phonenumber.
 4. The system of claim 3, wherein one or more of the callingparty entries includes an outgoing message identifier.
 5. The system ofclaim 4, wherein one or more of the calling party entries includes atleast one of a caller name and a caller address.
 6. The system of claim1, wherein the base unit comprises: a microphone configured to receive afirst outgoing message for storage in the first memory section as thedefault outgoing message; and, a button configured to activate recordingof the first outgoing message through the microphone.
 7. The system ofclaim 6, wherein an outgoing message received through the microphone ofthe base unit is stored in the first memory section as the defaultoutgoing message.
 8. The system of claim 6, wherein the handsetcomprises: a microphone configured to receive an outgoing message; and aradio transceiver configured to forward over a radio link to the baseunit the received outgoing message
 9. The system of claim 8, wherein thebase unit is further configured to automatically store the outgoingmessage received from the handset to the second memory section as acustom outgoing message.
 10. The system of claim 8, wherein: the handsetis configured to prompt a user to designate whether the outgoing messageis a custom outgoing message or a default outgoing message, and the baseunit is configured to store the outgoing message to the second memorysection in response to the user indicating that the outgoing message isa custom outgoing message, and to store the outgoing message to thefirst memory section in response to the user indicating that theoutgoing message is a default outgoing message.
 11. The system of claim8, wherein, the handset is configured to perform one or more of:retrieving information from the database; sending a newly-createdoutgoing message identifier to the base unit for storage in thedatabase; and sending a calling party number and an associated outgoingmessage identifier for storage in the database.
 12. The system of claim11, wherein the handset is configured to retrieve a calling party numberfor sending to the database of the base unit based upon a caller nameselected from a phone book database located in the handset.
 13. A methodof using a cordless telephone system, the cordless telephone systemhaving a base unit that is partitioned into at least a first memorysection and a second memory section that is different than the firstmemory section, the method comprising: storing a default outgoingmessage in the first memory section; storing a custom outgoing messagein the second memory section; determining that a calling party number ofa call is not contained in an outgoing message identifier database ofthe base unit; and in response to said determining, providing a promptduring the call to associate the calling party number with an outgoingmessage identifier of a database.
 14. The method of claim 13, furthercomprising: storing an outgoing message database in the base unitincluding at least one outgoing message identifier and at least onecalling party number associated with the at least one outgoing messageidentifier; receiving notification of a calling party numbercorresponding to an incoming call; querying the outgoing messagedatabase of the telephone to locate a calling party entry containing thecalling party number and an outgoing message identifier associated withthe calling party number; and playing an outgoing message stored in thesecond memory section that corresponds to the outgoing messageidentifier.
 15. The method of claim 14, wherein the receiving thenotification of the calling party number comprises using a caller IDdevice to identify the calling party number when an incoming call isreceived.
 16. The method of claim 14, wherein the querying the databasecomprises: determining if the calling party number is contained in thedatabase; and sending a signal to play the default outgoing messagestored in the first memory section if the calling party number is notcontained in the database.
 17. The method of claim 14, furthercomprising: receiving an outgoing message via a microphone of the baseunit in response to activation of a recording button of the base unit;and storing the received outgoing message in the first memory section asthe default outgoing message.
 18. The method of claim 14, furthercomprising: recording an outgoing message in the handset; and forwardingthe outgoing message from the handset to the base unit for storage. 19.The method of claim 18, further comprising: automatically storing theoutgoing message received from the handset in the second memory sectionas a custom outgoing message.
 20. A method of using a cordless telephonesystem, wherein the cordless telephone system includes an outgoingmessage identifier database of its a base unit that stores a pluralityof outgoing messages, and wherein the outgoing message identifierdatabase has a predetermined amount of storage that is available forstoring the outgoing messages, the method comprising: receiving anincoming telephone call via the base unit; determining that the callingparty number of the call is not contained in the outgoing messageidentifier database of the base unit; and in response to saiddetermining, providing a prompt during the call to associate the callingparty number with an outgoing message identifier of the database. 21.The method of claim 20, further comprising: presenting a list containinga plurality of outgoing message identifiers in response to the selectionof the calling party number for association; receiving a selection ofone among the plurality of outgoing message identifiers; and storinginformation including the calling party number and the selected oneamong the plurality of outgoing message identifiers in a calling partyrecord.
 22. The method of claim 21, wherein the storing the informationcomprises: sending the calling party number and selected one among theplurality of outgoing message identifiers from a handset of the cordlesstelephone system; and storing the information in a calling party recordof the database.
 23. The method of claim 22, further comprisingdisplaying the calling party number on a display of the handset.
 24. Themethod of claim 23, wherein the identifying the calling party numbercomprises using a caller ID function to determine the calling partynumber and to display the number on the handset.